Special Notes

As with any database, it is important to understand the "ownership" of the data in the database. The following lists represent the data that is shared by each component application, and the criteria used by LEAP Bridge Concrete to determine the "ownership" of the data shared.

Precast/Prestressed Girder

The following is a list of data shared by Precast/Prestressed Girder

Project Information	Project name Description User job number State Date By: (designer) State job number Specifications: (if not found in the LEAP Bridge Concrete database, or if there is no settings file, program will use "Standard Specifications (LRFD") Units (if not found in the database, the component program will use whatever is in its current settings file) Simple span or continuous span
Geometry Information	Overall width Skew angle start (for each span) Skew angle end (for each span) Haunch width and thickness Deck thickness Lane data (number of lanes and lane width) Span length information (precast beam lengths, bearing-to-bearing distances, etc., for both simple and multi-spans) Beam type and location
Material Information	Girder concrete properties Deck concrete properties Strand properties
Strand Pattern Information	For each beam which has a strand pattern Strand height/location (measured from bottom) Number of strands Straight or draped Debonded strand data Pull percentage
Rebar Information	For each beam with stirrups or negative reinforcement defined Stirrup bar size, legs, spacing Negative moment rebar, size and location
Results	For continuous spans, reactions due to dead and live loads on composite
Data Exchange Criteria	The following data exchange criteria is related to Precast/Prestressed Girder data exchange with LEAP Bridge Concrete: General: Precast/Prestressed Girder can read and load selected information such as Project, Geometry, Materials and Strand Pattern to the LB database (XML), if the database has not yet been modified (or created by Bridge Parametric Layout). If Bridge Parametric Layout is the component that creates the LEAP Bridge Concrete database (XML), then you can no longer make any changes to the Geometry related information within any of the analysis/design components. The user is still able to modify analysis/design data like Project, Materials and Strand Pattern information. Default Data: IfPrecast/Prestressed Girder is used as the entry point for creating a LEAP Bridge Concrete database: - A default Alignment, Vertical Profile and Cross-section is created. The default alignment length will be 1.5 times the length of the bridge in Precast/Prestressed Girder, starting at Station 0+00, and going upstation. - The default roadway will be the width of the bridge defined in Precast/Prestressed Girder, with no cross-slopes. - The default vertical profile starts at station 0+00 and goes up to the same station as the alignment, with all points along at an elevation of 100 feet. Precast/Prestressed Girder at this time can only analyze prismatic sections (i.e. start and end cross section is the same for any beam) Precast/Prestressed Girder will create in the LEAP Bridge Concrete database one default bearing (thickness of 6 inches) at each end of a beam, at the point of intersection of centerline of section and bearing location. Precast/Prestressed Girder can only handle both straight and flared girders. When reading in a file from LEAP Bridge Concrete that has flared girders, Precast/Prestressed Girder sets the Flared Girder checkbox on the Project tab to True. Precast/Prestressed Girder will write to the LEAP Bridge Concrete database a default pier cap based on width of bridge, bearing distances, etc., and the bearings at each interior support of a continuous span bridge. The 3-D graphic image of this information will be shown in LEAP Bridge Concrete only after processing through Bridge Parametric Layout. The 3-D graphics of the stirrups show the correct number of legs, diameter of bars and position along the length of the beam, but the stirrup shape is only a typical representative shape. Data Exchange Between Precast/Prestressed Girder and Components: If an analysis is completed in Precast/Prestressed Girder, the results for reactions due to dead loads and live loads on continuous spans are saved to the LEAP Bridge database, along with the other geometry information, by Precast/Prestressed Girder. If the bridge database was created initially by Precast/Prestressed Girder, and RC-PIER makes any changes to the superstructure parameters, it will not affect Precast/Prestressed Girder. Deck thickness, haunch width and haunch thickness in Precast/Prestressed Girder are considered to be constant for the entire bridge. In Bridge Parametric Layout, the bridge can have a deck thickness, and this is the data exchanged with LEAP Bridge Concrete. However, beam specific individual haunch thickness and width specified in Bridge Parametric Layout is not exchanged with Precast/Prestressed Girder. Camber and deflection values are not exchanged between Precast/Prestressed Girder and Bridge Parametric Layout at this time. Although Precast/Prestressed Girder saves material information (concrete, rebar and strand properties) to the LEAP Bridge Concrete database, neither Bridge Parametric Layout nor Substructure can make any changes to it. The 3-D graphics of strands designed by Precast/Prestressed Girder and shown in LEAP Bridge Concrete accurately represents the number of strands at each Layer (height). However, the horizontal layout of the strands is assumed to be uniformly distributed based on the thickness of the section at the particular layer.

Substructure

Following is a list of data shared between Substructure and LEAP Bridge Concrete. Aside from Project Information, the data mentioned below is needed for complete definition of a pier. Geometry information may not be modified after Bridge Parametric Layout was used to create a new LEAP Bridge Concrete database.

Project Information	Name Description Number State Date Designer Job number Specifications (if not found in the database, the program will default to whatever is in its current settings file or LRFD) Units (if not found in the database, the program will default to whatever is in its current settings file or LRFD)
Pier Definition	Pier Type Cap Type Column Type
Superstructure Information	Number of Lanes Beam Height Beam Section Area Beam Inertia (Ixx) Beam Inertia (Iyy) Beam C.G. Barrier/Railing Height Depth of Slab Span number near to current pier Bridge Overall Width Bridge Curb-to-Curb Distance Span Lengths for all spans
Cap Information	Start Elevation End Elevation Skew Cap depth (Z) Cap length (X) for straight and tapered caps Cap height (Y) for straight and tapered caps Cap non-tapered length (X) for tapered caps Cap minimum height (Y) at ends of tapered cap Cap segments length (X) and heights (Y) for variable caps for n segments Integral Cap dimensions (X1, X2, X3, X4, Y1, Y2, Y3, Z1) Cap Reinforcement (top/bottom bars and stirrups)
Column Information (for each column)	Location of column centerline from end of column Bottom Elevation For section at bottom: Width (X) Depth (Z) Chamfer (X) Chamfer (Z) For each additional section: - Distance from previous section (Y) - Width (X) - Depth (Z) - Chamfer (X) - Chamfer (Y) - Variation (which can be linear or parabolic) Drilled shaft (This is currently saved in private data in Substructure.) Column Reinforcement
Intermediate Strut Information	This information is not transferred to/from the XML database to RC-PIER.
Bearing Point Information	Single- or double-bearing line Eccentricities of bearing lines For each bearing point, its distance from end of cap or from previous bear. Measurement along the pier length. Integral superstructure web locations
Footing Information (for each footing)	Footing Isolated or Combined or Strap For Isolated footing: - Footing length (X) - Footing width (Z) - Footing depth (Y) - From Column Distance (X) for eccentric footing - Pile size and shape (supported shapes: rectangular, circular and H) - All pile locations for this footing For Combined footing: - Footing length (X) - Footing width (Z) - Footing depth (Y) - From Column Distance (X) for eccentricity - Pile size and shape (supported shapes: rectangular, circular and H) - All pile locations for this footing For Strap Footing: - Footing Head 1 length (X) - Footing Head 1 width (Z) - Footing Head 1 depth (Y) - Footing Head 2 length (X) - Footing Head 2 width (Z) - Footing Head 2 depth (Y) - Footing Strap width (Z) - Footing Strap depth (Y) - From Column Distance (X) for eccentricity - Pile size and shape (supported shapes: rectangular, circular and H) For All Footings: - Footing Reinforcement (X and Z direction bars)
Load Information	Continuous beam reactions at supports can be optionally read in if generation of dead loads or live loads is done with the option to use the reactions from Precast/Prestressed Girder is selected on the Dead Load or Live Load Generations dialog boxes.
Data Exchange Criteria	The following data exchange criteria is related to Substructure data exchange with LEAP Bridge Concrete: General: - Substructure cannot be used to create a new bridge database. If there is no bridge defined and the user starts Substructure, the user will be able to work with the 3 pier he/she defines within Substructure. However, he/she will not be able to create a new bridge database based on that pier. - Substructure can access only one pier at a time from the LEAP Bridge Concrete database. - Within Substructure, a user can define a pier at the beginning of the bridge instead of an abutment. However, LEAP Bridge Concrete by default generates an abutment at the ends of a bridge (which is a more common scenario). If the user would like to change abutment to a pier, the change and definition of the pier must be done in Bridge Parametric Layout. - Substructure defines the pier downstation. The user needs to pay special attention to the location of bearings, columns, cap elevations and cap sections. When Substructure loads data from the LEAP Bridge database it performs this data definition conversion automatically. Editing Modes: - Substructure works in different operating/editing modes depending on how the bridge database was created: * If the bridge in the database was created by Precast/Prestressed Girder, Substructure users can continue to change any pier geometry information freely. * If the bridge database was created by Bridge Parametric Layout, Substructure users cannot change any bridge or pier geometry definition (i.e. span lengths, bridge width, pier cap elevations, etc.) in Substructure. Superstructure Data: - The superstructure data entered in Substructure is not saved to the LEAP Bridge Concrete database. Pier Geometry: - Substructure assumes that the bridge is centered on the pier cap. Therefore, it is suggested that piers in Bridge Parametric Layout should also be defined in the same way if those need to be designed in Substructure. - At this time, pier caps have different definition criteria in Substructure, and Bridge Parametric Layout. Bridge Parametric Layout top surface of cap segments is always horizontal. However, in Substructure, the top surface of the cap is always considered to be a straight surface, from left end to right end of the cap, and Substructure does not consider the stepped-cap geometry. This means if an inclined cap is intended in Substructure, you need to have two or more segments for the cap within Bridge Parametric Layout. - Mixed column shapes are not allowed in Substructure. Therefore, if you need to transfer data for such a pier from Bridge Parametric Layout to Substructure, define all columns of the same shapes in Bridge Parametric Layout. - Flared circular columns are not allowed in Substructure. Therefore, if you need to transfer data for such columns from Bridge Parametric Layout to Substructure, define all flared circular columns as prismatic circular columns. All other flared columns (rectangular, rectangular chamfered, etc.) are allowed with linear and parabolic variation in Substructure. - In Substructure columns are defined with respect to bottom elevation of the column. However, in Bridge Parametric Layout and CIP RC/PT Girder, the columns are measured from top down. Therefore, when data is read or saved to the LEAP Bridge Concrete database, Substructure will make the appropriate conversion. - The bearing information entered in Substructure is not saved to the LEAP Bridge Concrete database. Therefore, if bearing locations need to be adjusted, it is better to do those in Precast/Prestressed Girder or Bridge Parametric Layout. - When Integral pier is read from Bridge Parametric Layout or CIP RC/PT Girder, the cap cross section diaphragm is assumed to be rectangular. - When reading an integral pier from Bridge Parametric Layout or CIP RC/PT Girder, if the cap dimensions are not specified, Substructure assumes the integral cap width to be equal to the largest column width. - Changes made in Substructure to Integral cap properties are not saved to the LEAP Bridge Concrete database.

CIP RC/PT Girder

Following is a list of data shared by CIP RC/PT Girder

Project Information	Project name Description User job number State Date By: (designer) State job number Specifications: (if not found in the LEAP Bridge database, or if there is no settings file, program will use LRFD) Bridge Type (slab/whole width) Units (if not found in the database, the component program will use whatever is in its current settings file) Loss Type
Geometry Information	The "Locked" flag below means that the data cannot be changed after the geometry is changed by Bridge Parametric Layout. "Not Locked" means that data can be changed in CIP RC/PT Girder even after Bridge Parametric Layout has specified the geometry. Geometry Information Alignment: LOCKED - All data including segment data, beginning station and offset to CL Bridge - Alignment Tie Layout: LOCKED - All connection types are written/read - abutments, piers, hinges - Bearing and Station - Support: NOT LOCKED Cross Section and section variation: NOT LOCKED - Diaphragms are saved in LEAP Bridge but ignored by GEOMATH Material Properties: NOT LOCKED Pier and Column Information (full set of capabilities): LOCKED - All pier types are written/read - integral, drop-cap; - All column types are written/read - circular, rectangular, rect-fillet, rect-chamfer, rect-bevel, general, defined as user-defined or program generated; - One pier can contain any combination of column types; - The column group is automatically centered on a pier in CBX - so, any not-centered location of the column group is changed; - Pier Material NOT LOCKED - Pier Support: NOT LOCKED
Model Information	Post-tensioning tendons, Longitudinal Rebars and Shear stirrups are written/read
Load Information	No Load Information is shared at this time
Assumptions and Limitations	Default roadway is created by CIP RC/PT Girder, but bridge width is not read by Bridge Parametric Layout - the width of the bridge is set by the roadway defined (being the roadway width at each cross section location). CIP RC/PT Girder can modify only the shape of the default roadway created by it, but only if the model was not read by Bridge Parametric Layout - after this moment, the roadways shape can be changed only by Bridge Parametric Layout. If Bridge Parametric Layout creates the bridge, CIP RC/PT Girder is not able to change any of the alignment or pier information.